Skip to content

partner integration docs v0#6262

Open
mshustov wants to merge 4 commits into
mainfrom
partner-docs
Open

partner integration docs v0#6262
mshustov wants to merge 4 commits into
mainfrom
partner-docs

Conversation

@mshustov
Copy link
Copy Markdown
Member

@mshustov mshustov commented May 22, 2026

Summary

Adds v0 Partner program documentation for external partners building ClickHouse integrations. This is interim onboarding content until a dedicated partner portal launches at the upcoming event.

New section at /integrations/partners with four pages:

  • Overview. reading order and links to the guides
  • Building integrations. ingestion (ClickPipes vs language clients), consumption, user-agent conventions, sandbox/trial access
  • Testing your integration. Cloud + OSS test matrix, type/scale/auth coverage, recommended example datasets
  • Documenting your integration. required doc sections, style rules, and a copy-paste PR skeleton for product pages

Navigation: new Partner program sidebar category under Integrations; tip callout on the Integrations landing page pointing partners to the guides


Note

Low Risk
Low risk: documentation-only additions plus a sidebar navigation update; main risk is broken links or misplaced sidebar entries.

Overview
Adds a new Integration development docs section under /integrations/integration-development with guides for building, testing, and documenting third-party ClickHouse integrations.

Updates the Integrations landing page with a :::tip pointing builders to these guides, and wires the new section into sidebars.js (plus _category_.yml) so it appears in the Integrations navigation.

Reviewed by Cursor Bugbot for commit d643cf0. Bugbot is set up for automated code reviews on this repo. Configure here.

@mshustov mshustov requested review from Amehla and alexfrancoeur May 22, 2026 10:42
@mshustov mshustov requested review from a team as code owners May 22, 2026 10:42
@vercel
Copy link
Copy Markdown

vercel Bot commented May 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clickhouse-docs Ready Ready Preview May 24, 2026 12:22pm
4 Skipped Deployments
Project Deployment Actions Updated (UTC)
clickhouse-docs-jp Ignored Ignored May 24, 2026 12:22pm
clickhouse-docs-ko Ignored Ignored Preview May 24, 2026 12:22pm
clickhouse-docs-ru Ignored Ignored Preview May 24, 2026 12:22pm
clickhouse-docs-zh Ignored Ignored Preview May 24, 2026 12:22pm

Request Review

@mshustov mshustov changed the title partner integration v0 partner integration docs v0 May 22, 2026
@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 22, 2026

Docs PR opened: ClickHouse/mintlify-docs-dev#46

Added a four-page Partner program section guiding partners on building, testing, and documenting ClickHouse integrations.

Copy link
Copy Markdown
Contributor

@alexfrancoeur alexfrancoeur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is amazing, thank you @mshustov 🙏 🙏 🙏 🙏

I dropped in comments that are more around positioning (integration development vs. partner focused) and some others around identification, etc. I think we can probably talk through these things, come to an agreement, and I'm happy to help update the docs based on where we land.

Comment thread docs/integrations/partners/_category_.yml Outdated
Comment thread docs/integrations/partners/building-integrations.md Outdated
Comment thread docs/integrations/integration-development/building-integrations.md

## Sandbox and trial access {#sandbox-and-trial-access}

[ClickHouse Cloud](https://clickhouse.com/cloud) offers a free trial for development and integration validation. Partners enrolled in the formal program receive additional development credits; details will be available in the partner portal.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Amehla we should clarify what's available in the partner portal and how much we should lean on this narrative in these docs. My thinking is that we make this more generic vs. pointing to the partner portal. For this one specifically, I think it's fine if we say something like -- "if you are a House Mate and partner, you can get credits in the partner portal"


## Where docs live {#where-docs-live}

- **Repository:** [`ClickHouse/clickhouse-docs`](https://github.com/ClickHouse/clickhouse-docs)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

open question -- do we want partner docs in our docs? I initially assumed we'd be pushing docs back to the partner and referencing them from our integration pages and drill downs. @Amehla let us know how you were thinking about it. Either would work, these are OSS. It definitely gives us more CH eyes on them on an opportunity to validate the changes as @mshustov suggests below.

Comment thread docs/integrations/partners/documenting-your-integration.md Outdated
Comment thread docs/integrations/partners/testing-your-integration.md Outdated
Comment thread docs/integrations/index.mdx Outdated
| Partner integrations | Built or maintained, and supported by, third-party software vendors |
| Community integrations | Built or maintained and supported by community members. No direct support is available besides the public GitHub repositories and community Slack channels |

:::tip Building a partner integration?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Amehla we'll need the stubbed link for the partner portal and sign up page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants